-
Notifications
You must be signed in to change notification settings - Fork 464
Fix Bazel build #3181
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Fix Bazel build #3181
Conversation
|
@swift-ci please test |
This comment was marked as off-topic.
This comment was marked as off-topic.
e02e0c0 to
e05854f
Compare
|
Could you please approve the workflow once more, @keith? |
|
Started |
e05854f to
4008b89
Compare
4008b89 to
535dfce
Compare
|
@swift-ci please test |
|
cc @ahoppen is it ok to add a non-blocking job for this? |
|
I’m personally fine with running the Bazel tests in GitHub Actions (thanks for adding them) but I’d like to hear @bnbarham’s opinion as well before merging. |
bnbarham
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adding the PR test SGTM under the same guidelines as the original bazel support was added, ie. you're happy to fix any issues that come up (#1251 (review)). And having PR testing should only help with that I imagine :)
|
@swift-ci please test |
Building with Bazel doesn't work at the moment. That's mainly due to the missing dependencies for
SwiftRefactorTestandSwiftSyntaxMacros. However, there is also an issue withrules_pythonwhich gets fixed by the update of the Bazel version.To alleviate the risk of causing an outdated Bazel configuration again, I also added an action that at least builds everything in PRs.